-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CSS 6730 - add ofga model tests #1243
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nice.. a few comments, but generally lgtm
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for this. But can you please put the instructions on how to use the CLI at the top of the YAML file.
openfga/tests.fga.yaml
Outdated
- model:mo-1 | ||
- model:mo-2 | ||
writer: | ||
- model:mo-1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
mo-1 is listed in both of these, but I see we only explicitly grant user:mo-1 admin access to model:mo-1. So I'm surprised it appears under both in list_objects. I need to go read the docs on what list_objects is doing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's because of this:
- user: user:*
relation: administrator
object: model:mo-2
list_objects checks whether the relations you've listed fully match those of a given object, that's why you need to list models accessible by everyone too.
…ator relation of serviceaccount
Description
This PR includes tests that fully cover JIMM's authorisation model and ensure no breaking changes are introduced. Since OpenFGA doesn't have a procedure to alter existing models we need to verify the model behaves as expected, and that future changes to it don't break the intended behavior. It also adds the tests as a CI step.
Jira issue: CSS-6730
Engineering checklist